get_proposal

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

States 'Read-only', which is a key behavioral trait, but no annotations exist; description does not cover error handling, auth requirements, or rate limits. Adequate but minimal.

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?

Extremely concise: 8 words plus 'Read-only.' Front-loaded with the action and resource, no wasted text.

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?

Given the simplicity (1 param, no output schema), the description sufficiently covers what the tool does. Could mention what 'complete details' includes, but not essential.

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 coverage is 100% and the description merely echoes the schema's parameter description ('Portal proposal ID.') without adding meaning or constraints (e.g., type, range). Baseline score 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?

Description clearly states the verb 'Get' and resource 'complete details for one Portal.io proposal', distinguishing it from siblings like list_proposals (which lists multiple) or search_catalog (which searches different entities).

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?

Implies usage when needing single proposal details, but provides no explicit when-not-to-use or alternatives (e.g., when to use list_proposals instead).

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