platformFees.list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'List' implies read-only access, the description does not confirm safety, disclose pagination behavior (despite the 'limit' parameter), indicate what fields are returned, or mention rate limits.

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 extremely brief (4 words), which prevents bloat, but it is under-specified rather than efficiently concise. Given the lack of schema documentation and annotations, this brevity represents insufficient coverage rather than appropriate sizing.

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?

Given the absence of annotations, output schema, and schema parameter descriptions, the description should provide comprehensive context. It fails to explain what 'platform fees' represent, what data structure is returned, or how pagination behaves, leaving the agent with minimal operational context.

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 description must compensate by explaining parameter semantics. It fails entirely—the description does not explain what 'ascending' sorts by (date, amount, ID?) or that 'limit' controls pagination page size, leaving both parameters undocumented.

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 clearly states the verb (List) and resource (Ryft platform fees), providing basic purpose identification. However, it fails to distinguish from sibling tool 'platformFees.get' (which retrieves a specific fee by ID) or clarify that this returns multiple records without filtering capabilities.

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?

No guidance is provided on when to use this tool versus 'platformFees.get' for retrieving specific fees, or when to use 'platformFees.getRefunds'. There are no stated prerequisites, filtering limitations, or workflow recommendations.

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