spraay_sctp_po_by_id

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

Annotations already declare readOnlyHint=true. Description adds cost ($0.005) and explicitly states 'Read-only', reinforcing but not adding significant new behavioral context beyond annotations.

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 concise sentences front-loaded with purpose, cost, read-only nature, and usage. Every sentence earns its place with no fluff.

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 output schema exists and tool is simple (one parameter), description is complete. It covers purpose, cost, read-only behavior, and parameter usage without needing return format details.

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% with description 'Path parameter that identifies the resource'. Description adds minimal clarification: 'to fetch a single record' — baseline score as schema already covers semantics.

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 'Get purchase order', specifying the verb and resource. It distinguishes from sibling spraay_sctp_po by emphasizing 'by id' and 'fetch a single record', making purpose unambiguous.

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?

Tells user to 'Provide the path parameter to fetch a single record'. Implicitly guides that if you have an ID, use this tool; otherwise use spraay_sctp_po. Lacks explicit exclusion of alternatives but sufficient.

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