Show Generic Tool Item

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

Annotations already indicate readOnlyHint=true, etc. The description adds that it returns a JSON object and lists required parameters, but it does not explain the behavior of the page and per_page parameters (e.g., are they for related data?). No contradictions with 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?

The description is concise (3 sentences) and front-loaded with the primary purpose. It includes necessary details (required params, API info) without extraneous content.

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 read-only tool without an output schema, the description covers the resource, required parameters, API endpoint, and return type (JSON object). It also provides Procore API location context. However, it does not explain the role of page/per_page parameters, which could be important for users.

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?

The input schema has 100% description coverage for all 4 parameters, so the schema already provides meaning. The description reiterates two required parameters (project_id, id) but adds no additional context beyond the schema. The page/per_page parameters are not mentioned in the description.

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 clearly states the action ('Get the details') and the resource ('a single Generic Tool Item', 'Custom - Configurable Tools'). It distinguishes from siblings like list_generic_tool_items by specifying it fetches full details of a single item by identifier.

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 phrase 'Use this to fetch the full details' clearly indicates when to use the tool. However, it does not explicitly mention when not to use it or provide alternatives like list_generic_tool_items for querying multiple items.

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