assess_togaf_readiness

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

The description discloses numerous behavioral traits beyond the annotations: advisory nature, scoring algorithm (seven checks, score range, status thresholds), guarantee that 'limited' is the floor, and the error condition (ModelNotFoundError). This adds significant value given the tool has readOnlyHint and openWorldHint annotations that only hint at safety and completeness.

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 well-structured with clear sections (advisory, scoring, returns, errors) and front-loads the core purpose. It is slightly verbose—especially the return list—but every sentence serves a purpose. A minor trim would improve conciseness without losing clarity.

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 tool with 2 optional parameters and an output schema (implied), the description covers behavior, scoring interpretation, and error conditions comprehensively. However, the lack of input parameter explanations leaves a gap, preventing a perfect score. The output schema is mentioned, so return value details aren't strictly needed, but the description still documents them thoroughly.

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?

With 0% schema description coverage, the description should explain the two parameters (include_hard_validation, include_quality_assurance_views), but it does not. It focuses solely on the output structure. While the schema provides names and defaults, the description adds no meaning about what these boolean flags control or their effects.

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 tool returns 'advisory TOGAF-oriented readiness findings' and distinguishes it from validation tools by emphasizing its advisory nature. The verb 'assess' combined with 'readiness findings' makes the purpose specific and distinct from sibling tools like validate_model or build_quality_report.

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 explicitly says 'Advisory only' and explains that the compliance_claim is always false, indicating it should be used for review, not formal conformance. It provides scoring context but does not directly mention when to avoid using it or list alternative tools for conformance checking, which would strengthen guidance.

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