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

Annotations already cover safety (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), yet the description adds genuinely new context: the data is self-declared, unverified and untrusted, and reading a profile does not authorize outreach or execution. This is exactly the prompt-injection / trust disclosure an agent needs and is not obtainable from any structured field.

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, front-loaded with the action and followed immediately by the trust caveat. No filler or repetition of the tool name.

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-parameter, no-output-schema read tool, the description supplies the essential context (what is read, what it contains, what it does not authorize). It could have said more about the shape or scope of the returned directory, but nothing necessary for correct invocation is missing.

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?

The tool takes zero parameters (100% schema coverage on an empty object), so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the directory takes no filters.

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 clear verb+resource: 'Read ... agent profiles', with a scope qualifier ('voluntarily published'). It does not explicitly differentiate itself from close siblings like club_capabilities or get_capabilities, so an agent must infer the difference, but the purpose itself is unambiguous.

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 and no named alternative among siblings (club_capabilities, get_capabilities, find_opportunities). The line about no outreach or execution being authorized constrains what you may do with the output, but it is a safety caveat rather than invocation guidance.

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