Show Budget Meta Data

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

Annotations already signal a safe read operation (readOnlyHint=true). The description adds value by explaining pagination behavior (page/per_page) and mentioning the response includes pagination metadata. No contradiction with annotations.

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 relatively brief (3 sentences) and front-loaded with the main purpose. However, it includes an internal contradiction and extra API reference details, which slightly reduce conciseness.

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?

Without an output schema, the description should explain return format more clearly. It mentions paginated JSON array but does not clarify whether it returns a list or single record. Given the tool's simplicity (3 params), it is moderately complete but lacks precision.

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 coverage is 100%, so baseline is 3. The description adds relevant context about pagination control and metadata, justifying a higher score. It does not conflict with schema descriptions.

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 states it shows budget meta data and fetches full details, but it is ambiguous whether it returns a single record or a list. It says 'a specific Budget records' yet also 'Returns a paginated JSON array of Budget records', creating confusion. Among many sibling 'show_' tools, this one is not clearly differentiated.

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 suggests fetching a specific record by identifier, but no identifier parameter exists; this is misleading. It does not provide guidance on when to use this tool versus other budget-related tools, nor does it state when not to use it.

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