read_rules

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

Annotations already disclose readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by clarifying that reading the guide does not register the agent, though it does not describe permissions, return format, or document freshness beyond 'current'.

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 short sentences are front-loaded with the core action and then the key exclusion. There is no redundant or filler text.

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 read-only, one-parameter policy-reading tool with no output schema, the description provides enough to select and invoke it correctly. It could be more complete by clarifying the meaning of each document option, but the annotations and enum cover the main gaps.

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 schema has 0% description coverage for the single 'document' parameter, so the description should compensate, but it only refers broadly to 'API guide and policies' and never explains or distinguishes the enum values skill, ethics, terms, and privacy. The enum labels alone carry the parameter semantics.

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 uses a specific verb+resource ('Read current API guide and policies') and explicitly distinguishes the tool from registration by stating 'Does not register an agent.' This lets an agent separate it from the sibling register_agent tool without inspecting the schema.

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?

It gives an explicit usage condition ('before joining') and an explicit exclusion/alternative behavior ('Does not register an agent'), so the agent knows both when to use it and what it must not be used for.

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