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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds meaningful context beyond that: ratings are aggregated anonymously in a public monthly report and never surfaced as customer reviews, which tells the agent the data's downstream use. It doesn't describe the response, but this is a small submission tool.

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?

Two compact sentences, front-loaded with 'Optional' and the core action, with privacy and cost details after. Every clause carries useful information.

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?

For a simple three-parameter submission tool with no output schema and safe annotations, the description covers purpose, cost, and data handling. Only a hint about what happens on success or invalid input is missing, which is minor.

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%, so the schema already documents score, reason, and would_pay. The description adds the 1-5 range (already in schema) and 'short reason' emphasis but no new semantics, so the baseline of 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 ('Rate how well StartupHub.ai served this task') with an explicit 1-5 scale, so the action is unambiguous. It does not name or contrast with siblings like check_domain_rating, but those are clearly ratings of other entities rather than of the service itself.

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?

'Optional' sets the when-to-use expectation, and 'Free, no API key' removes the main reason an agent might hesitate. It lacks an explicit when-not condition (e.g., only after completing a task), but the context is clear.

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