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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine scope context by declaring two exclusions: no contract rules and no document bodies, which prevents an agent from misusing this as a full-document read. However, it says nothing about result_offset behavior, result size, or whether project_id must be an existing/accessible project.

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?

A single dense sentence that front-loads the core action and the key exclusion, with the returned field list following. Nothing is redundant, though the long comma-separated field list is slightly hard to parse.

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?

There is no output schema, so the description usefully enumerates the returned fields in prose and rules out document bodies. But for a two-parameter tool with a paging parameter and zero schema documentation, it leaves the agent without enough to know how result_offset affects the read or how the per-document instructions are keyed.

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 0% and the description mentions neither parameter. With two undocumented parameters, an agent gets no explanation of project_id's expected form or of result_offset's purpose (presumably paging into the instructions collection), so the description fails to compensate for the schema gap.

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 names a specific verb ('Read') and resource ('the method') and then enumerates the exact contents returned: project instructions, per-document instructions, format_template, load policy and limits, rules_version, and method version. It also differentiates itself from a sibling by scoping out 'the contract rules', so an agent can distinguish it from read_contract without opening a 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?

Usage is only implied: 'Read the method alone, without the contract rules' suggests using this when contract rules are not needed, but it never names read_contract as the alternative or states the condition that selects between them. The reader must infer when this is the right call versus read_contract or read_project.

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