get_agents_md_constraints

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. It states the tool 'returns' data but does not confirm read-only behavior, error handling for missing files, or any side effects. The description gives minimal transparency beyond the basic action.

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 sentences, direct and to the point, with no redundant information. It front-loads the key action and additional context about automatic enforcement, earning its length.

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 no output schema and sibling tools that could overlap, the description fails to explain the return format, parameter usage, or how this tool relates to get_constraints. It is incomplete for an agent to reliably call without additional knowledge.

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 two parameters (project_dir, file_path) with 0% description coverage, and the description does not explain their purpose or expected values. No added meaning beyond the schema; the agent must guess how to use these parameters.

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's action: parsing specific files (AGENTS.md, CLAUDE.md, etc.) and returning declarative constraints. It distinguishes itself from siblings by specifying the exact file sources and noting its automatic enforcement role, making it clear what resource it targets.

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 implies this tool is for inspection of constraints that are automatically enforced via PreToolUse, but it does not explicitly compare to alternatives like get_constraints or provide when-not-to-use guidance. The usage context is hinted but not fully articulated.

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