Get Discovery Report

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

Annotations already declare readOnlyHint=true. The description adds no further behavioral details, but it does not contradict the annotations. It confirms the read-only nature by stating it 'shows' data.

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 two precise sentences with no filler. Every word adds value, front-loading the core purpose.

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?

While lacking an output schema, the description lists key output components. For a simple, single-parameter read tool, this is adequate but could benefit from clarifying 'AI readiness' scope.

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 the product_id parameter described as 'Product/entity UUID'. The description does not add meaning beyond this, resulting in a baseline score.

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 tool retrieves an 'AI readiness and discovery report' for a product, listing specific outputs (entity details, trust score, data completeness). This distinguishes it from sibling tools like nanmesh.entity.get (basic entity details) and nanmesh.trust.summary (trust-only).

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?

No explicit guidance on when to use this tool over alternatives is given. However, the description's specificity about AI readiness implies its unique use case, which a capable agent may infer.

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