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

No annotations are provided, so the description carries the full disclosure burden. It does add real value by naming the payload ('resolution rules + example config'), which is the only hint at the return shape since there is no output schema. However, it says nothing about auth requirements, behavior for an invalid template_id, or errors.

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?

One sentence, front-loaded with the verb and resource, with zero filler. It is arguably too terse for the missing parameter and usage detail, but as pure conciseness it is strong.

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 simple single-record read the description is minimally viable: it names the resource and the returned payload, which partly offsets the absent output schema. It remains incomplete on the required template_id and on when to prefer the list sibling.

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% for the single parameter, template_id, so the description must compensate and it does not — the parameter is never mentioned. An agent gets no format, source, or validity guidance for the id beyond its name.

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 verb and resource: 'Read a single market template'. The word 'single' implicitly distinguishes it from the sibling pax.composer_templates_list, but it never names that sibling or explicitly contrasts with it, so the differentiation is left to inference.

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 statement of when to use this tool versus pax.composer_templates_list or pax.composer_proposal_submit, and no prerequisites (e.g. that a valid template_id is required). Usage is only weakly implied by 'single'.

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