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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: a 2 MB cap surfaced as `truncated: true`, BEGIN/END markers carrying a per-bundle random token so marker-lookalikes inside content can be told apart, an explicit trust model distinguishing admin rules from team-member data, and the warning that it carries no versions so a get_doc read is required before mutation.

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?

Front-loaded with the headline and the 'fastest way' framing, which is good. But the opening sentence repeats the title verbatim, and the middle is a chain of dense run-ons (template list, flags, D-spec citations) that could be tightened into a short bulleted structure without losing 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?

There is no output schema, so the description must describe the return value — and it does: overall shape, ordering, per-doc markers, the linked-projects line, the status table with WIP limits, template fields and computed flags, and the truncation signal. Given a single-parameter read tool, nothing an agent needs to interpret the result 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?

Only one parameter, project_key, and the schema already fully documents its pattern and format at 100% coverage. The description does not add meaning about the parameter itself, so the high-coverage 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 resource and form — 'A project's context as one markdown text' — and then enumerates exactly what is bundled: company/project briefs, working notes, open handoffs, status meanings, template fields, default role rules. That enumeration distinguishes it from siblings like get_doc (single doc) and get_project (metadata), so an agent can choose it without opening another 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?

Explicitly frames it as 'The fastest way to get a project's context' and 'Useful before working on a project you do not know,' and routes the agent onward for the adjacent cases: read missing docs with get_doc, call get_doc before changing a doc, take field ids from here for create_issue/update_issue/search_issues. When-to-use, when-to-use-something-else, and downstream use are all covered.

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