get_project_info

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

The description uses the verb 'Read', implying it is read-only and non-destructive. It specifies the required path format. Without annotations, this conveys adequate behavioral context for a simple read operation.

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?

Two sentences: first states purpose, second gives parameter guidance. No wasted words, front-loaded with key information.

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 simple tool with one parameter and no output schema, the description lists the returned fields (AGP version, Kotlin version, modules list, project name). It is adequate, though a more explicit format or structure would enhance completeness.

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%, and the description adds extra semantic detail by specifying that the project path must be to the root containing settings.gradle.kts, which is not implicit from the schema alone.

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 reads root Android project info, listing specific data points (AGP version, Kotlin version, modules list, project name). It distinguishes from siblings which read specific files like gradle or manifest.

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 instructions on how to use the tool: pass the absolute path to the project root containing settings.gradle.kts. However, it does not explicitly state when to use this tool versus siblings, though it is implied.

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