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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: 'Owner-only — 403 for anyone else,' which tells the agent an authorization failure mode exists and not to retry as a different caller. It doesn't mention ordering or result-size behavior, but that's minor for a read.

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?

Three short sentences, each doing distinct work: what it lists, who may call it, and what to do next. The access constraint is front-loaded and there is no filler.

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?

With no output schema, the parenthetical field list carries the return-value burden, and the 403 note covers the main failure mode, so an agent has enough to call and interpret it. Only pagination/ordering behavior for large response sets is left unaddressed.

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 100%, with needId documented as 'The UUID of your need' and apiKey pointing to register. The description implies needId ('one of your needs') but adds no format, constraint, or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('list the seller responses to one of your needs') and even enumerates the returned fields (seller, offer, price, note), so the agent knows exactly what comes back. It separates itself from the seller-side counterpart (respond_to_need) by scoping to the need owner, though it never names that sibling explicitly.

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?

Clearly frames the owner-side viewing context and then routes the agent forward: 'To go ahead with a response, call agentpact.propose_deal with that needId and offerId.' That is concrete next-step guidance with the exact parameters to carry over. It stops short of stating when-not-to-use or naming alternatives for viewing responses.

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