tentra

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the tool persists data and returns a contract_id, it doesn't disclose important behavioral traits like whether this is a write operation (implied but not stated), what permissions are needed, whether it's idempotent, error conditions, or rate limits. For a tool that appears to create records with 6 parameters, this is insufficient behavioral context.

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 perfectly concise - a single sentence that communicates the core purpose and the key output value. Every word earns its place, with no wasted text or redundancy. It's front-loaded with the main action and follows with the practical consequence (returns contract_id).

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 tool's apparent complexity (6 parameters, no annotations, no output schema), the description is minimally adequate but leaves significant gaps. It explains what the tool does and what it returns, but doesn't cover error conditions, side effects, or how the persisted contract integrates with the broader system. The lack of output schema means the description should ideally say more about the return value format beyond just 'contract_id'.

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 description doesn't add any parameter-specific information beyond what's already in the input schema, which has 100% coverage with detailed descriptions for all parameters. The baseline score of 3 is appropriate since the schema does all the heavy lifting, though the description could have provided context about how parameters relate to each other or usage patterns.

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 specific action ('persist'), the resource ('service contract'), and the destination ('to the code graph'). It distinguishes from siblings by mentioning the return value (contract_id) and referencing bind_contract, which is a sibling tool. This provides clear differentiation from other tools like get_contracts or analyze_codebase.

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 provides clear context by stating this is for persisting service contracts and mentions the return value is used with bind_contract, giving implicit guidance on when to use this tool. However, it doesn't explicitly state when NOT to use it or mention alternatives among the many sibling tools, which prevents a perfect score.

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