rate_agent

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

No annotations provided, but description discloses single-use constraint, wallet requirement, and impact on reputation system. Does not explicitly state idempotency or side effects, but sufficient for a rating action.

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?

Concise and front-loaded: first sentence states the action, followed by key usage details. 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?

Given no output schema, description explains the purpose and constraints but does not describe return behavior or error scenarios. However, for a simple rating tool, it provides adequate context.

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 coverage is 100%, so description primarily reinforces schema info (rating_token from hire, stars 1-5). Adds context like 'single-use per receipt' but does not provide new parameter-specific semantics beyond what schema offers.

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 'Submit a rating after a hire' with specific verb and resource, distinguishing it from siblings like hire_agent and check_reputation.

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?

Explicitly tells when to use (after a hire, using rating_token) and provides constraints (single-use per receipt, requires wallet). Could be improved by noting when not to use, but context is clear.

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