get_prospect_post_section

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

No annotations are provided, so the description must carry the behavioral burden; 'Read-only' is a useful, explicit safety claim for a fetch operation. However, it says nothing about failure behavior (invalid/missing ID), permissions, or scoping, which is thin for a tool with no structured annotation coverage.

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 very short sentences with the operation stated first and nothing wasted. It is efficiently front-loaded, though it stops short of being information-dense.

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 one-parameter fetch with an output schema and full schema coverage, the definition is nearly sufficient, and 'Read-only' compensates for the absence of annotations. The main gap is that the provenance of the ID and its relationship to sibling tools is not stated in the description.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains where the ID comes from. The description adds only 'by ID', which does not meaningfully extend the schema, so the baseline 3 is appropriate.

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 ('Get a prospect post section by ID'), so an agent knows exactly what entity is fetched. It does not differentiate itself from the sibling list_prospect_post_sections, though that linkage appears only in the schema, not the description.

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?

The description gives no guidance on when to use this versus list_prospect_post_sections or other lookups. The only routing hint ('from list_prospect_post_sections') lives in the parameter schema description, not in the tool description itself.

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