list_assets_cc

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

Describes return fields (success, assets list, error) clearly. No annotations provided, but the description carries the burden well, indicating a read-only retrieval without side effects.

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?

Concise, with clear structure using dashes for return fields. Could be slightly more organized (e.g., separate lines), but overall efficient.

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?

Sufficient for a parameterless list tool: explains what it returns and error handling. Lacks differentiation from sibling 'list_all_assets', but otherwise 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?

Input schema has no parameters, so description adds value by explaining the output schema in detail. Schema coverage is 100%, but the description compensates with return field documentation.

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?

Clearly states it retrieves all available assets, specifying they are 'integration plans'. Provides return structure. However, it does not explicitly differentiate from sibling 'list_all_assets', which may cause confusion.

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?

Implies usage when needing all integration plan assets, but no explicit when-to-use or comparison with alternatives like 'list_all_assets'. No usage exclusions provided.

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