search_projects

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

With no annotations, the description carries the full burden. It does add genuine behavioral context beyond the schema: the upstream endpoint, the data source AISafety.com, and a CC-BY-4.0 license with an attribution obligation. However, it says nothing about read-only nature, pagination behavior, rate limits, or result format, so the disclosure is partial.

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, content type front-loaded. The URL and licensing sentences are legal/provenance boilerplate rather than tool semantics, but they are required for compliant use, so they earn their place. 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?

For a zero-required-parameter search tool with a fully documented schema and no output schema, the description covers what the resource is and where the data comes from. It is missing the routing information an agent needs to pick it over its ten siblings, which is the main completeness gap.

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 q, limit, and status are all fully documented in the schema itself. The description adds no additional syntax or format detail for any parameter, making the baseline 3 correct.

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 gives a content type ('Volunteer and collaboration opportunities') but never states the action — the verb is carried entirely by the name 'search_projects'. It does not distinguish this resource from any of the ten sibling search_* tools, which each target a different content type. The purpose is inferable but vague.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives, despite ten sibling search tools covering adjacent domains (communities, organizations, jobs, etc.). The agent is left to guess when a 'project' is the right resource versus a community or organization.

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