get_score

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

Annotations are absent, requiring the description to carry full behavioral disclosure burden. While 'detailed' hints at data granularity, the description lacks information on read-only safety, caching, rate limits, authentication requirements, or error conditions.

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?

Extremely efficient seven-word sentence with strong front-loading (verb-first). No redundancy or filler content; every word serves the definitional purpose.

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?

Adequate for a single-parameter lookup tool with complete schema documentation, though 'AN Score' jargon is unexplained and the lack of output schema means the return structure is only vaguely indicated ('detailed breakdown').

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?

Schema provides 100% coverage with 'slug' documented as 'Service slug to look up'. The description adds no parameter-specific guidance, meeting the baseline score for high-coverage schemas.

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?

Clear verb 'Get' and specific resource 'AN Score breakdown' identifies what the tool retrieves, though it doesn't explicitly differentiate from sibling 'get_' tools (get_alternatives, get_ledger, etc.) beyond implicit resource naming.

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 on when to use versus alternatives like get_alternatives or check_balance, no prerequisites mentioned, and no indication of when this lookup is appropriate versus other service-related tools.

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