platformFees.get

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate what happens if the ID is not found (error vs null), what the return payload contains, or whether this operation is idempotent/read-only (though implied by 'Get', it is not stated).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no waste. However, it may be overly terse given the lack of annotations and output schema, leaving insufficient room for necessary behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter retrieval tool, the description covers the basic operation. However, given the absence of an output schema, parameter descriptions, and annotations, the description should ideally include more context about the return value or error conditions to be considered complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the schema provides no parameter descriptions. The description adds minimal semantic value by stating 'by id', which clarifies that the 'id' parameter is used for lookup. However, it does not describe the ID format, constraints (beyond minLength 1), or where to obtain it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('Ryft platform fee') and includes the scope modifier 'by id', which effectively distinguishes it from the sibling tool 'platformFees.list'. However, it does not explain what constitutes a 'platform fee' in this context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings (platformFees.list, platformFees.getRefunds) or prerequisites like obtaining the ID from a previous list call. No explicit when/when-not guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.