get_customer

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

No annotations provided, and description only states a read operation. No disclosure of authentication requirements, caching, idempotency, or possible side effects. For a simple getter, some transparency on data freshness or authorization would be beneficial.

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?

Description is a single, front-loaded sentence that directly states purpose and outputs. No unnecessary words.

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 parameterless tool with no output schema, the description adequately conveys return details (plan, credits, billing). However, it lacks mention of authentication or error conditions, which could affect completeness.

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?

Tool has zero parameters, and schema coverage is 100% (vacuously). Description appropriately adds no parameter info beyond what's already clear. Baseline 4 applies for no parameters.

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?

Description clearly states the tool retrieves subscription info, specifically plan, credits, and billing. It is distinct from sibling get_* tools which handle bookmarks, collections, reads, etc.

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?

Description implies usage for subscription info retrieval but lacks explicit guidance on when to use this versus alternatives or conditions. No exclusions or prerequisites are mentioned.

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