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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds useful content about what the payload contains and a caution against over-reading JOB-RECORDS.md, but says nothing about size, cost, or whether the templates are static or profile-dependent.

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?

It is a single compact sentence fragment with the primary artifact front-loaded, so nothing is bloated. But the fragment lacks a verb and packs three artifacts plus a conditional into one clause, making it denser than it needs to be for the amount of information conveyed.

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?

An output schema exists, so return values need not be explained, but two enum parameters with zero schema coverage are completely unaddressed and no usage context for the tool itself is given. For a tool whose output changes shape based on tier and host_profile, this leaves the agent without enough to choose parameters confidently.

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%, so the description carries the full burden for tier (quick/standard/deep) and host_profile (parallel/sequential/pack) — and it never mentions either. The enum values hint that output may be scoped by tier and execution profile, but that effect is left entirely to guesswork.

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 is a noun list of three artifacts (JOB-METHOD.md, JOB-RECORDS.md, delivery templates) rather than a verb-plus-resource statement; only the title ('Read the team method and templates') supplies the action. An agent can infer it fetches these documents, but the tool name 'get_job_templates' does not obviously match 'team method and records', leaving a small reconciliation gap.

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 one concrete conditional: open JOB-RECORDS.md only when advance_job refuses a record, which usefully routes a sub-resource lookup. However, nothing says when to call this tool at all, whether it is a prerequisite for advance_job or start_job, or how it relates to siblings like get_job_preferences.

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