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. It only states 'Get' (implying a read) but does not mention data scope, freshness, authentication needs, or whether the period parameter affects the output. The description adds minimal context beyond the action itself.

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 concise (five words) and front-loaded, but it is under-specified rather than appropriately sized. It omits critical information about the parameter and expected behavior, so brevity comes at the cost of completeness.

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 one parameter, no annotations, and no output schema, the description is severely incomplete. It does not explain what the financial summary contains, how the period parameter works, or when to call this tool instead of related ones. The agent lacks essential context for correct invocation.

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 description coverage is 0%, and the description does not mention the 'period' parameter at all. Although the enum values (month/quarter/year) hint at time periods, the description fails to explain how period affects the financial summary, so the parameter semantics are largely uncommunicated.

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 'Get QuickBooks financial summary' clearly states a specific verb (Get) and resource (QuickBooks financial summary). It is distinguishable from sibling write tools like qb_create_invoice and qb_record_payment, though it does not explicitly differentiate from similar read tools like get_expenses or get_stripe.

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 provides no guidance on when to use this tool versus alternatives, such as get_expenses or get_stripe. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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